Curse

ShadeZeRO · Apr 30, 2005, 09:16 PM // 21:16

Which AMD chipsets are you all using?

im using the K8T800 Pro, and with the Sound Blaster Audigy 2 ZS card....

hmm, im going to try and disable the sound and then play, is there a -nosound boot key for GW?

explode9339 · Apr 30, 2005, 09:19 PM // 21:19

The problem isnt with soundcards because I have an on-board sound, again, it seems that most of us have amd chipsets (i have nforce 2)

Anywhow, I tried many fixes and nothing worked, BUT, someone told me to defrag my HD, and I did that - no crashes since - and I have played a solid 12 hours. =) So, My advice, defrag the HD your GW is installed on and see what happens - it worked for me!!!

Also, I did change one other thing, and Im not sure if this is what fixed it or the defragging, but I ran my memory timings VERY tight, 2,3,3,8, and I changed them to 2,3,3,11 , So I changed teh last memory timing from 8 to 11, I was reading somewhere that AMD chipsets ran better this way.. Either way, since I changed that timing and defragged I have had ZERO crashes, and I used to crash every 30 minutes... Give it a try all and see what happens!

-Ex

ShadeZeRO · Apr 30, 2005, 09:25 PM // 21:25

Ill try that out, but for ram timings...anything over 8 for the TRAS is over excessive. (TRAS is the 4th #)

explode9339 · Apr 30, 2005, 09:30 PM // 21:30

Shade, I know it sounds counterintuitive, but do a google search on RAM Timings and nforce2 or AMD chipsets and you will find that many people argue that 11 is better than even 5... give it a try, see what happen

-Ex

VikingBlade · Apr 30, 2005, 09:55 PM // 21:55

Quote:

Originally Posted by explode9339

The problem isnt with soundcards because I have an on-board sound, again, it seems that most of us have amd chipsets (i have nforce 2)

Anywhow, I tried many fixes and nothing worked, BUT, someone told me to defrag my HD, and I did that - no crashes since - and I have played a solid 12 hours. =) So, My advice, defrag the HD your GW is installed on and see what happens - it worked for me!!!

Also, I did change one other thing, and Im not sure if this is what fixed it or the defragging, but I ran my memory timings VERY tight, 2,3,3,8, and I changed them to 2,3,3,11 , So I changed teh last memory timing from 8 to 11, I was reading somewhere that AMD chipsets ran better this way.. Either way, since I changed that timing and defragged I have had ZERO crashes, and I used to crash every 30 minutes... Give it a try all and see what happens!

-Ex

I don't think it's defragging. To tell you the truth, I have no idea why people suggest defragging to fix any computer problem (besides slow disk access, though more so on non-NT OS). Defragging should fix no problems.

ShadeZeRO · Apr 30, 2005, 10:04 PM // 22:04

well, the 11 on the TRAS is better for nforce2 supposidly, but what about the other chipsets such as k8t800, etc.

Bone_White_Haze · Apr 30, 2005, 10:06 PM // 22:06

Same problem, intel chipset here, not AMD. Latest drivers all around, no issues with any other games.

Symptoms: BSODs, hard reboots with no BSOD, snap shutoff with no reboot.

BSOD's have referenced Win32k.sys (no surprise there), NV4_disp.dll (part of the GeForce driver), and the scary one (once) NFTS.sys (that's hard drive, nooooo do NOT roach my drive).

Not a virus. Not spyware. Not heat. Not a memory problem (at least nothing I can find with testing). Not an old driver. Not old hardware.

It looks like it's the game. Or possibly SP2.

Run a DXDIAG on every machine that punts, run all the tests, save the results, and send it in to the techs, perhaps they can track down what all these machines have in common.

Voodoods · Apr 30, 2005, 10:58 PM // 22:58

AMD 64 3500+
gig RAM
ASUS A8V Mobo
Nvidia 6800GT
AC'97 onboard sound

All drivers shiny

Started crashing once the game went live. This has nothing to do with anything but GW period. I run a backup utility and restored to my previous config and I have no issues until I install this game.

ShadeZeRO · Apr 30, 2005, 11:04 PM // 23:04

hmm, i just defraged, and set TRAS at 11.
For the first time it worked for an hour and half (1.5hrs)...but when i changed a visual setting in the game it BSOD, but not a regular BSOD, it just shut off and went blue. I'm going to try it again and see what happens.

Voodoods · Apr 30, 2005, 11:51 PM // 23:51

This is the output of a minidump that happened awhile ago- seems Nvidia is the issue, though its still exclusive to GW:

************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

UNEXPECTED_KERNEL_MODE_TRAP_M (1000007f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 00000008, EXCEPTION_DOUBLE_FAULT
Arg2: 80042000
Arg3: 00000000
Arg4: 00000000

Debugging Details:
------------------

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

FAULTING_MODULE: 804d4000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4182ec49

BUGCHECK_STR: 0x7f_8

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

LAST_CONTROL_TRANSFER: from 00000000 to f69644db

STACK_TEXT:
f7c47ffc 00000000 00000000 00000000 00000000 nv4_mini+0x324db

FOLLOWUP_IP:
nv4_mini+324db
f69644db ?? ???

SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: nv4_mini+324db

MODULE_NAME: nv4_mini

IMAGE_NAME: nv4_mini.sys

STACK_COMMAND: kb

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner

ShadeZeRO · May 01, 2005, 12:13 AM // 00:13

ok, looks like its still being a lil punk. Although now it runs for more then 30 seconds ingame, now its like 15 minutes or more depending.

Velora · May 01, 2005, 12:18 AM // 00:18

Our problem is with Intel.

Although I've had Ath64/ATI/Soundblaster + game issues on my other machine with other products.

Rememdium · May 01, 2005, 12:21 AM // 00:21

After another defrag, I'm getting consistently longer times too, but the same problem persists...

kinda hard to find a group when you've got this hanging over your head, huh?

ShadeZeRO · May 01, 2005, 12:22 AM // 00:22

so how about defragging before each play! That would be horrible AND annoying...

I wish i could just defrag that 1 directory...

Pharalon · May 01, 2005, 02:36 AM // 02:36

OK, those having crashing problems, try running the game with the -nosound command line option. For those that don't know how to do this, right-click on your guild wars shortcut, go to properties, and change the Target field to something like this

"G:\Games\Guild Wars\Gw.exe" -nosound

You'll have no sound, but just put on winamp or something in the background

If that seems to fix the crashing issues, report it to tech support, it'll help the devs out a lot. There was a similar issue a while back with onboard NForce2 boards sound (sound would drop out, game would crash soon after), but that's since been resolved I believe.

Hope that helps.

King Kizer · May 01, 2005, 02:51 AM // 02:51

Heyas, I have the same problem when I play Guild Wars (it seems to be Guild Wars only, no other games, even Half-Life 2, WoW and Doom 3 don't do this) quite often I will be playing and my monitor will go black and the little light will go red. I thought it might be my refresh rate so I turned it to default in-game and back to 60 on my desktop but that didn't fix it. I also tried running in Windowed mode.

I can't even get back to my desktop after this happens and am forced to shut off my computer by hand and turn it back on...

My Specs are:
P4 2.8ghz 800mhz FSB, GeForce 6800 128, Neo2 Mobo, 512 Ram, 120g HD.

I'll go ahead and run with no sound until it's fixed, thanks for the support on the topic thus far.

ShadeZeRO · May 01, 2005, 02:56 AM // 02:56

The nosound trick, does not work for me. Still BSOD, especially when i try to turn on 4xAA.

Rememdium · May 01, 2005, 03:30 AM // 03:30

Well, that was interesting.

I was doing a mission where I had to kill a Charr boss (who was one level higher than I am). I couldn't do enough damage (he could heal himself) so it was basically a stalemate. I went back into town and got some henchmen (I won't group because of the crashing problem) and we proceed to take on the boss... mid fight (boss still alive, mind you) the game crashes... I come back after the reboot and the contact has a ! over his head.

Apparently, my henchmen completed my mission for me.

Just something to lighten the mood in this thread a bit.

Kyokuji · May 01, 2005, 04:25 AM // 04:25

Also getting this problem on my computer.
I'm using a Radeon 9600 so it can't be Nvidia exclusive.
I have not had this problem with any other games.

It's too bad, I'm really enjoying this game, but having my computer restart on me every 10 minutes isn't a good way to play.

King Kizer · May 01, 2005, 04:32 AM // 04:32

The Nosound thing did not work for me either... I tried installing the new Omega Drivers but that didnt help. Gah!